Summary

Fixes #332 — 7 bugs in @ruvector/router that made SemanticRouter completely non-functional through the wrapper and partially broken when used directly.

• Critical: wrapper passed wrong property name (dimensions vs dimension) — constructor always threw
• Critical: wrapper called non-existent methods (addRoute, match, matchTopK, removeRoute)
• High: native module returns distances (0=identical) but JS filtered as similarities (1=identical) — routing always returned empty
• High: fresh DB crashed on count()/get() — redb tables don't exist until first write
• High: multiple VectorDb instances fought over ./vectors.db file lock
• Medium: addIntentAsync silently dropped intents without embedder or embedding
• Medium: version mismatch — package 0.1.28, platform deps pinned to 0.1.27

Files Changed

Test plan

• node npm/packages/router/test.js — all checks pass locally (darwin-arm64)
• CI builds all 5 platforms (linux-x64, linux-arm64, darwin-x64, darwin-arm64, win32-x64)
• CI publishes platform packages + main package to npm
• Verify npm install @ruvector/router resolves correct platform binary

Test Results (local)

✓ VectorDb instance created (384 dimensions, cosine distance, in-memory)
✓ count(): 0
✓ insert() worked
✓ search() returned 1 result(s)
✓ SemanticRouter instance created
✓ addIntent() worked
✓ routeWithEmbedding() returned 1 result(s)
  Top result: test-intent (score: 1.0000)

🤖 Generated with claude-flow